home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d19
/
dorpch37.arc
/
README.NOW
< prev
next >
Wrap
Text File
|
1991-01-01
|
5KB
|
99 lines
January, 1, 1991 IMPORTANT - PLEASE READ
For a description of changes in this release see CHANGES.DOC
Big problems: QuickBASIC 4.0 cannot be used.
Please read our comments in the DOC regarding
our choice of QuickBASIC 3.0. We are, however,
working on routines that may lead to the
capability to use QuickBASIC 4.x. No promises!
The files contained herein work with QuickBASIC 3.0 only.
I've included a file: CLE.BAT for compiling and linking the example door.
This is Release 3.7 of DOORPCH. It is a complete replacement for
any previous version in your possession. The previous version was 3.5.
You will require Microsoft (R) QuickBASIC 3.0 compiler to use
DOORPCH 3.7. All the necessary files are contained within this ZIP file
and should ALWAYS be distributed together as a unit.
Many hours of hard work have gone into this release. The logic contained
herein came from Raymond Clements, Clint Labarthe, Terry Shockley,
Harold Thompson, and Ben Perron.
If you haven't ever written a DOOR before then read on in the DOCS and see
just how easy it is! We have even provided an example DOOR program
demonstrating just a few of the capabilities of DOORPCH 3.7. For those of
you that are upgrading, we have provided you upward compatibility - more
or less. Most all the functions continue to work. The GETIN2.ASC code has
been replaced in a small part by DOORPCH.END. The majority and all new
code is in DORPCH37.EXE which is now used by the QB compiler during
compilation. A LINKER.BAT file is provided for you to LINK your program
(.OBJ) into an executable module (.EXE).
You may have to patch your BRUN30.EXE file. Included are instructions
on how to do this. If you require a version and/or feel uncomfortable
modifying yours, then call one of our BBS's and download it. Either
include the patched BRUN30.EXE with each of your DOORS or provide a way
for other SysOps to download the patched version.
Please read ALL the DOCS before proceeding. Much has changed.
Functionality abounds. You really owe it to yourself (and me too!) to
read thru this. If you have any questions, call my BBS and ask for
assistance. If a bug is detected, please let me know right away.
NOTE: Six IMPORTANT new things.......
1) In your batch files, you MUST now remove the /NETWORK
parameter if it currently exists. It is no longer
needed/supported.
Failure to do this will result in a run-time error.
2) Also - AND VERY IMPORTANT -
A NEW variable has been added which MUST be set BEFORE
the INCLUDE for DOORPCH.BEG. It is NODE%.
If your program uses disk data files that must be
shared AND you have file locking logic then set
NODE% = 1.
If you DO NOT have disk data files then set NODE% = 1.
If you DO have disk data files AND DO NOT have
file locking logic then set NODE% = 0. This variable
when set to equal to <1> will allow the DOOR to run
on multiple nodes concurrently. If this variable is
found set to zero, then DOORPCH will only allow it to
run on ONE NODE CONCURRENTLY. Please BE CAREFUL.
3) On existing DOORNAME.CFn files used by DOORS LINKed to version
3.4 of DOORPCH, you MUST delete the first record - COM1 or
COM2. This information is obtained from the BBS files by
DOORPCH.
4) The PROGNAME$ and R.ELEASE$ strings MUST be populated BEFORE
entering the logic in DOORPCH.BEG. They should be populated
with your DOOR name and release version respectively.
(ie. PROGNAME$ = "4 Card Solitare": R.ELEASE$ = "v1.5").
5) The PROGB$ string MUST be populated BEFORE entering the
logic in DOORPCH.BEG. It should be populated with the
BATCH (or PROGRAM) name. (ie. PROGB$ = "4CARD")
6) You MUST set two variables in AUTOEXEC.BAT for your BBS system.
Place the following statements any place in AUTOEXEC.BAT:
SET DOORPCH=PCB (for prior DoorPch compatibility)
SET LIB=<path to DORPCH37.EXE>
If you get an error during the DOORPCH initialization process it
is probably due to an incorrectly configured .CFG file or the
parameter passed to your door (ie. 4CARD 4CARD.CFG) is probably
incorrect. It may be due to one of the six things listed above.
Thanks,
Raymond Clements - The Pegasus BBS - (502)684-9855 or (502)684-9871 HST